Fix: restore pnpm for changeset publish to apply publishConfig.exports#618
Merged
Fix: restore pnpm for changeset publish to apply publishConfig.exports#618
Conversation
changeset publish only applies publishConfig overrides (like exports) when using pnpm publish. The bun migration changed packageManager to bun, causing changeset to fall back to npm publish which ignores publishConfig.exports. - Add pnpm setup step to release workflow - Temporarily swap packageManager to pnpm before changeset publish in release script so changeset detects pnpm and uses pnpm publish Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
FL4TLiN3
force-pushed
the
fix/publish-config-exports
branch
from
658e0b4 to
8458c37
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
changeset publishonly appliespublishConfigoverrides (likepublishConfig.exports) when it detects pnpm and usespnpm publishpackageManagerfrompnpm@10.10.0tobun@1.3.5, causing changeset to fall back tonpm publishwhich ignorespublishConfig.exportsexports: { ".": "./src/index.ts" }instead of the correct dist paths, making them unresolvable by consumersChanges
packageManagertopnpm@10.10.0(bun ignores this field, so day-to-day dev is unaffected)pnpm-workspace.yaml(turbo needs it whenpackageManageris pnpm)pnpm publishis availableTest plan
bun run typecheck— 23/23 passbun run format-and-lint— passbun run test— 19/19 passbun run build— 23/23 passbun run check-deps— pass🤖 Generated with Claude Code